Enhancement Of New Radio PUSCH For URLLC In Mobile Communications

ABSTRACT

Various examples and schemes pertaining to enhancement of New Radio (NR) physical uplink shared channel (PUSCH) for ultra-reliable low-latency communication (URLLC) in mobile communications are described. An apparatus determines whether to apply a cyclic delay diversity (CDD) scheme for a PUSCH transmission. The apparatus performs the PUSCH transmission to a network node of a wireless network with the CDD scheme applied responsive to determining that the CDD scheme is to be applied. Optionally, the apparatus receives a signaling from the network node indicating information related to mini-slot repetition such that the apparatus performs the PUSCH transmission with at least one symbol repeated in multiple mini-slots within a slot. Optionally, the apparatus also performs a transport block size (TBS) calculation for the PUSCH transmission with an assumption of no demodulation reference signal (DMRS) in the TBS calculation.

CROSS REFERENCE TO RELATED PATENT APPLICATION(S)

The present disclosure is part of a non-provisional application claimingthe priority benefit of U.S. Patent Application No. 62/755,587, filed on5 Nov. 2018, the content of which being incorporated by reference in itsentirety.

TECHNICAL FIELD

The present disclosure is generally related to mobile communicationsand, more particularly, to techniques pertaining to enhancement of NewRadio (NR) physical uplink shared channel (PUSCH) for ultra-reliablelow-latency communication (URLLC) in mobile communications.

BACKGROUND

Unless otherwise indicated herein, approaches described in this sectionare not prior art to the claims listed below and are not admitted asprior art by inclusion in this section.

In Release 15 (Rel-15) of the 3^(rd) Generation Partnership Project(3GPP) specification, multiple mechanisms were specified for improvementof PUSCH reliability and latency such as a new modulation coding scheme(MCS) table, slot aggregation for reliability, and support of mini-slot(PUSCH mapping type B) where the length of the PUSCH can be one throughfourteen symbols and the starting symbol can be any position within aslot as a useful latency enhancement. However, there is still room forimprovement in areas such as support of intra-slot mini-slot repetitionand UL diversity schemes such as cyclic delay diversity (CDD), which areneeded for URLLC use-cases to improve latency, reliability and spectralefficiency.

SUMMARY

The following summary is illustrative only and is not intended to belimiting in any way. That is, the following summary is provided tointroduce concepts, highlights, benefits and advantages of the novel andnon-obvious techniques described herein. Select implementations arefurther described below in the detailed description. Thus, the followingsummary is not intended to identify essential features of the claimedsubject matter, nor is it intended for use in determining the scope ofthe claimed subject matter.

In one aspect, a method may involve a processor of an apparatusdetermining whether to apply a CDD scheme for a PUSCH transmission. Themethod may also involve the processor performing the PUSCH transmissionto a network node of a wireless network with the CDD scheme appliedresponsive to determining that the CDD scheme is to be applied.

In one aspect, a method may involve a processor of an apparatusreceiving a signaling from a network node of a wireless networkindicating information related to mini-slot repetition. The method mayalso involve the processor performing a PUSCH transmission to thenetwork node with at least one symbol repeated in multiple mini-slotswithin a slot.

In one aspect, a method may involve a processor of an apparatusdetermining whether to apply a CDD scheme for a PUSCH transmission. Themethod may also involve the processor receiving a signaling from anetwork node of a wireless network indicating information related tomini-slot repetition. The method may further involve the processorperforming a transport block size (TBS) calculation for the PUSCHtransmission with an assumption of no demodulation reference signal(DMRS) in the TBS calculation. The method may additionally involve theprocessor performing the PUSCH transmission to the network node with theCDD scheme applied responsive to determining that the CDD scheme is tobe applied and with at least one symbol repeated in multiple mini-slotswithin a slot.

It is noteworthy that, although description provided herein may be inthe context of certain radio access technologies, networks and networktopologies such as Ethernet, the proposed concepts, schemes and anyvariation(s)/derivative(s) thereof may be implemented in, for and byother types of radio access technologies, networks and networktopologies such as, for example and without limitation, 5th Generation(5G), NR, Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro,narrowband (NB), narrowband Internet of Things (NB-IoT), Wi-Fi and anyfuture-developed networking and communication technologies. Thus, thescope of the present disclosure is not limited to the examples describedherein.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are included to provide a furtherunderstanding of the disclosure and are incorporated in and constitute apart of the present disclosure. The drawings illustrate implementationsof the disclosure and, together with the description, serve to explainthe principles of the disclosure. It is appreciable that the drawingsare not necessarily in scale as some components may be shown to be outof proportion than the size in actual implementation in order to clearlyillustrate the concept of the present disclosure.

FIG. 1 is a diagram of an example network environment in which varioussolutions and schemes in accordance with the present disclosure may beimplemented.

FIG. 2 shows an example scenario in accordance with an implementation ofthe present disclosure.

FIG. 3 shows an example scenario in accordance with an implementation ofthe present disclosure.

FIG. 4 is a block diagram of an example communication system inaccordance with an implementation of the present disclosure.

FIG. 5 is a flowchart of an example process in accordance with animplementation of the present disclosure.

FIG. 6 is a flowchart of an example process in accordance with animplementation of the present disclosure.

FIG. 7 is a flowchart of an example process in accordance with animplementation of the present disclosure.

DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS

Detailed embodiments and implementations of the claimed subject mattersare disclosed herein. However, it shall be understood that the disclosedembodiments and implementations are merely illustrative of the claimedsubject matters which may be embodied in various forms. The presentdisclosure may, however, be embodied in many different forms and shouldnot be construed as limited to the exemplary embodiments andimplementations set forth herein. Rather, these exemplary embodimentsand implementations are provided so that description of the presentdisclosure is thorough and complete and will fully convey the scope ofthe present disclosure to those skilled in the art. In the descriptionbelow, details of well-known features and techniques may be omitted toavoid unnecessarily obscuring the presented embodiments andimplementations.

Overview

Implementations in accordance with the present disclosure relate tovarious techniques, methods, schemes and/or solutions pertaining toenhancement of NR PUSCH for URLLC in mobile communications. According tothe present disclosure, a number of possible solutions may beimplemented separately or jointly. That is, although these possiblesolutions may be described below separately, two or more of thesepossible solutions may be implemented in one combination or another.

FIG. 1 illustrates an example network environment 100 in which varioussolutions and schemes in accordance with the present disclosure may beimplemented. FIG. 2 and FIG. 3 illustrate example scenarios 200 and 300,respectively, in accordance with implementations of the presentdisclosure. Each of scenarios 200 and 300 may be implemented in networkenvironment 100. The following description of various proposed schemesis provided with reference to FIG. 1-FIG. 3.

Referring to FIG. 1, network environment 100 may involve a UE 110 inwireless communication with a wireless network 120 (e.g., a 5G NR mobilenetwork). UE 110 may initially be in wireless communication withwireless network 120 via a base station or network node 125 (e.g., aneNB, gNB or transmit-receive point (TRP)). In network environment 100,UE 110 and wireless network 120 may implement various schemes pertainingto enhancement of NR PUSCH for URLLC in mobile communications inaccordance with the present disclosure, as described herein.

With respect to transmit diversity for URLLC UL transmissions, NR dataUL transmission has precoding schemes to enhance performance,particularly for channels with short delay spread and low mobility. Onthe other hand, according to simulation, it may be demonstrated that atransmit diversity scheme (e.g., non-transparent CDD) may outperformprecoding in case the targeted error rate is lower than 10⁻². FIG. 2shows a diagram of example scenario 200 in which the channel setting isperfect for precoding. However, the block error rate (BLER) curve slopeof CDD is more decent and shows potential advantage in case BLER is 10⁻³or lower. For URLLC applications operating at very low BLER target,there may still be room for enhancement of the transmission scheme.

Regarding comparison between precoding and a transmit diversity scheme(e.g., non-transparent CDD), with CDD delay confined to about one-fifthcyclic precoding (CP), it can be observed that precoding can be betterthan or comparable to CDD for BLER down to 10⁻². The slope of CDD canbecome steeper with CDD delay increased to about one-third CP. In FIG. 2no delay value is included as there is loss in channel estimationperformance due to excessive delay spread which may not bring betterperformance than a shorter CDD delay at BLER of 10⁻². Nevertheless, incase the BLER slope is the key for performance at BLER of 10⁻⁵, a largerCDD delay may be considered in various implementations.

Thus, under various proposed schemes in accordance with the presentdisclosure, a CDD scheme (e.g., non-transparent CDD) may be applied inUL transmissions (e.g., PUSCH) for URLLC to enhance UL transmitdiversity. Under a proposed scheme, use or application of CDD (e.g.,non-transparent CDD) may be limited to grant-based or configured grant.Under a proposed scheme, use or application of CDD (e.g.,non-transparent CDD) may be limited to a certain targeted reliability.Under a proposed scheme, use or application of CDD (e.g.,non-transparent CDD) may be limited to certain MCS table(s). Under aproposed scheme, use or application of CDD (e.g., non-transparent CDD)may be limited to certain radio network temporary identifier(s)(RNTI(s)). For instance, use or application of CDD (e.g.,non-transparent CDD) may be limited to a new MCS-RNTI. Under a proposedscheme, use or application of CDD (e.g., non-transparent CDD) for ULtransmissions may be defined as a UE feature or a UE capability of UE110.

With respect to signaling for aggregation type, under Rel-15 of the 3GPPspecification, when UE 110 is configured with aggregationFactorDL>1, thesame symbol and resource block (RB) allocation is applied across anumber of consecutive slots equal to aggregationFactorDL. UE 110 mayexpect that the transport block (TB) is repeated within each symbolallocation among each of the aggregationFactorDL consecutive slots.Aggregation factor 1, 2, 4 or 8 is semi-statically configured separately(e.g., not part of a table). In Rel-15, the number of repetition fordata corresponds to the layer 1 (L1) parameter “aggregation-factor-DL”and when this field is absent UE 110 applies the value of 1, which meansthe repetition is disabled. UE 110 may be radio resource control(RRC)-configured with aggregationFactorDL for downlink (DL)transmissions and aggregationFactorUL for UL transmissions.

In Rel-16 of the 3GPP specification, mini-slot repetition intra-slot andinter-slot could be introduced. This mechanism is different to theRel-15 mini-slot/slot aggregation. Therefore, the differentiationbetween the two mechanisms should be captured in the 3GPP specificationand signaled to UE 110.

Under a proposed scheme in accordance with the present disclosure, toindicate to UE 110 the mini-slot repetition, multiple options may beadopted by wireless network 120. Under a first option (option 1), aseparate RRC (or dynamic) parameter may be defined, which may be calledrepetitionFactor for example, and may operate similarly asaggregationFactor. This parameter (repetitionFactor) may indicate thenumber of contiguous or non-contiguous repetitions intra-slot orinter-slot. When this field is absent, UE 110 may apply the value 1. Thenew repetition factor may have different possible values thanaggregationFactor. With option 1, the new Rel-16 repetition factor andRel-15 aggregationFactor may be enabled simultaneously unless arestriction to discard this possibility is specified.

Under a second option (option 2), the Rel-15 parameter aggregationFactormay be re-used for mini-slot repetition. A new RRC (or dynamic)parameter may be defined to differentiate between the Rel-15 aggregationand the Rel-16 mini-slot repetition. With option 2, the new Rel-16repetition factor and Rel-15 aggregationFactor may not be enabledsimultaneously since once single RRC flag would be used to switchbetween them.

Regarding the repetition pattern, there may be two options under theproposed scheme. For instance, the repetitions may be contiguousrepetitions (e.g., back-to-back repetitions). Alternatively, therepetitions may be non-contiguous repetitions. In an event thatnon-contiguous repetition is supported, a repetition offset may bedefined and signaled by network node 125 to UE 110 (e.g., RRC ordynamically) to indicate the offset between adjacent repetitions interms of a number of orthogonal frequency-divisional multiplexing (OFDM)symbols. The offset may be defined as the number of symbols between alast symbol of one repetition and a first symbol of an immediatelysubsequent repetition or as the offset between starting symbols of twosuccessive repetitions.

The non-contiguous repetition may be useful to add more flexibility tosupport early termination and, hence, improve the resource efficiency(but may impact latency). Under the proposed scheme, DMRS sharing may bedisabled for non-contiguous repetitions. In an event that semi-staticUL/DL assignment configuration shows a conflict with scheduledrepetitions, the repetitions in conflict may be omitted in the countingrather than postponed.

Regarding redundancy version (RV) indices, there may be differentoptions under the proposed scheme in an event that all the repetitionsare scheduled with the same single downlink control information (DCI)signaling. For instance, the RV field in the DCI may be utilized forscheduling the transmission to indicate the RV of the first repetitionand the subsequent repetitions will cycle through the RV in order 0, 2,3, 1 starting from the RV indicated in the DCI. Alternatively, RVindices may be fixed to 0→2→3→1 all the time and the RV index in the DCIsignaling may not be necessary. This may help reduce the DCI size (forcompact DCI) and the RV bitfield may no longer be needed. It isnoteworthy that, regarding crossing a slot boundary, the repetitions maybe allowed to cross a slot boundary and the scrambling for thismini-slot DMRS may be clarified.

Support of mini-slot repetition in the same slot (or even crossing slotboundaries) may be an important enhancement as it allows for multipletransmission opportunities of the same TB in the same slot. This mayfurther improve the reliability and latency, as well as help meetingURLLC requirements. However, when mini-slots are used (e.g., twoorthogonal-symbol (OS) mini-slots) and when repetitions within the sameslot are allowed, the repetitions may use the same DMRS configuration.This may lead to a very high DMRS overhead which is sub-optimal and notnecessarily needed to meet targeted performance even for fading channelsor high mobility.

Thus, under a proposed scheme in accordance with the present disclosure,DMRS sharing between the repetitions may be utilized to reduce DMRSoverhead. Under the proposed scheme, DMRS may be removed or reduced fromcertain repetition(s). FIG. 3 shows an example scenario 300 of DMRSreduction. In particular, part (A) of FIG. 3 shows DMRS configuration ofType-1/Type-B mapping/single-symbol, with a high DMRS overhead which isnot needed to meet targeted URLLC performance. Part (B) of FIG. 3 showsDMRS sharing across mini-slots.

In an event that DMRS sharing is disabled, DMRS definition andconfiguration may continue using the specification (e.g., section 6.4.1of Technical Specification (TS) 38.211) and additional DMRS may betransmitted according to the scheduling type and the duration (e.g., asspecified in Table 6.4.1.1.3-3 of TS38.211 for frequency hoppingdisabled and specified in Table 6.4.1.1.3-6 of TS38.211 for frequencyhopping enabled).

In an event that DMRS sharing is enabled, one possible solution tospecify the DMRS density and the DMRS OS position may be to consider agroup of repetitions as a single mini-slot. For instance, two mini-slotsof two OS's each may be considered as a single mini-slot of four OS's,and the same specification (e.g., section 6.4.1 of TS38.211) may bere-used.

In an event that DMRS sharing is enabled, the number of resourceelements (REs) for DMRS per physical resource block (PRB), N_(DMRS)^(PRB), in the scheduled mini-slot may change from one repetition to thenext. This may impact the TB size (TBS) determination and may lead to adifferent TBS calculated from one repetition to the next unless the usedMCS has also changed from one repetition to the next and the new MCS issignaled to UE 110. However, in case there is only a single DCIscheduling the repetition, only a single MCS may be signaled to UE 110.Therefore, under a proposed scheme in accordance with the presentdisclosure, UE 110 may maintain the same TBS calculated from the DCI forall the repetitions scheduled by the same DCI. That is, UE 110 mayassume no DMRS in the TBS calculation. The effective code rate maychange from one repetition to another to exploit the REs freed from theDMRS overhead.

Illustrative Implementations

FIG. 4 illustrates an example communication system 400 having an exampleapparatus 410 and an example apparatus 420 in accordance with animplementation of the present disclosure. Each of apparatus 410 andapparatus 420 may perform various functions to implement schemes,techniques, processes and methods described herein pertaining toenhancement of NR PUSCH for URLLC in mobile communications, includingvarious schemes described above as well as processes described below.

Each of apparatus 410 and apparatus 420 may be a part of an electronicapparatus, which may be a UE such as a vehicle, a portable or mobileapparatus, a wearable apparatus, a wireless communication apparatus or acomputing apparatus. For instance, each of apparatus 410 and apparatus420 may be implemented in an electronic control unit (ECU) of a vehicle,a smartphone, a smartwatch, a personal digital assistant, a digitalcamera, or a computing equipment such as a tablet computer, a laptopcomputer or a notebook computer. Each of apparatus 410 and apparatus 420may also be a part of a machine type apparatus, which may be an IoT orNB-IoT apparatus such as an immobile or a stationary apparatus, a homeapparatus, a wire communication apparatus or a computing apparatus. Forinstance, each of apparatus 410 and apparatus 420 may be implemented ina smart thermostat, a smart fridge, a smart door lock, a wirelessspeaker or a home control center. Alternatively, each of apparatus 410and apparatus 420 may be implemented in the form of one or moreintegrated-circuit (IC) chips such as, for example and withoutlimitation, one or more single-core processors, one or more multi-coreprocessors, one or more complex-instruction-set-computing (CISC)processors, or one or more reduced-instruction-set-computing (RISC)processors. Each of apparatus 410 and apparatus 420 may include at leastsome of those components shown in FIG. 4 such as a processor 412 and aprocessor 422, respectively. Each of apparatus 410 and apparatus 420 mayfurther include one or more other components not pertinent to theproposed scheme of the present disclosure (e.g., internal power supply,display device and/or user interface device), and, thus, suchcomponent(s) of each of apparatus 410 and apparatus 420 are neithershown in FIG. 4 nor described below in the interest of simplicity andbrevity.

In some implementations, at least one of apparatus 410 and apparatus 420may be a part of an electronic apparatus, which may be a vehicle, aroadside unit (RSU), network node or base station (e.g., eNB, gNB orTRP), a small cell, a router or a gateway. For instance, at least one ofapparatus 410 and apparatus 420 may be implemented in a vehicle in avehicle-to-vehicle (V2V) or vehicle-to-everything (V2X) network, aneNodeB in an LTE, LTE-Advanced or LTE-Advanced Pro network or in a gNBin a 5G, NR, IoT or NB-IoT network. Alternatively, at least one ofapparatus 410 and apparatus 420 may be implemented in the form of one ormore IC chips such as, for example and without limitation, one or moresingle-core processors, one or more multi-core processors, or one ormore CISC or RISC processors.

In one aspect, each of processor 412 and processor 422 may beimplemented in the form of one or more single-core processors, one ormore multi-core processors, or one or more CISC or RISC processors. Thatis, even though a singular term “a processor” is used herein to refer toprocessor 412 and processor 422, each of processor 412 and processor 422may include multiple processors in some implementations and a singleprocessor in other implementations in accordance with the presentdisclosure. In another aspect, each of processor 412 and processor 422may be implemented in the form of hardware (and, optionally, firmware)with electronic components including, for example and withoutlimitation, one or more transistors, one or more diodes, one or morecapacitors, one or more resistors, one or more inductors, one or morememristors and/or one or more varactors that are configured and arrangedto achieve specific purposes in accordance with the present disclosure.In other words, in at least some implementations, each of processor 412and processor 422 is a special-purpose machine specifically designed,arranged and configured to perform specific tasks including enhancementof NR PUSCH for URLLC in mobile communications in accordance withvarious implementations of the present disclosure.

In some implementations, apparatus 410 may also include a wirelesstransceiver 416 coupled to processor 412 and capable of wirelesslytransmitting and receiving data over a wireless link (e.g., a 3GPPconnection or a non-3GPP connection). In some implementations, apparatus410 may further include a memory 414 coupled to processor 412 andcapable of being accessed by processor 412 and storing data therein. Insome implementations, apparatus 420 may also include a wirelesstransceiver 426 coupled to processor 422 and capable of wirelesslytransmitting and receiving data over a wireless link (e.g., a 3GPPconnection or a non-3GPP connection). In some implementations, apparatus420 may further include a memory 424 coupled to processor 422 andcapable of being accessed by processor 422 and storing data therein.Accordingly, apparatus 410 and apparatus 420 may wirelessly communicatewith each other via transceiver 416 and transceiver 426, respectively.

To aid better understanding, the following description of theoperations, functionalities and capabilities of each of apparatus 410and apparatus 420 is provided in the context of an NR communicationenvironment in which apparatus 410 is implemented in or as a wirelesscommunication device, a communication apparatus, a UE or an IoT device(e.g., UE 110) and apparatus 420 is implemented in or as a base stationor network node (e.g., network node 125).

In one aspect of enhancement of NR PUSCH for URLLC in mobilecommunications in accordance with the present disclosure, processor 412of apparatus 410 may determine whether to apply a CDD scheme (e.g.,non-transparent CDD) for a PUSCH transmission. Additionally, processor412 may perform, via transceiver 416, the PUSCH transmission toapparatus 420 as a network node (e.g., network node 125) of a wirelessnetwork (e.g., wireless network 120) with the CDD scheme appliedresponsive to determining that the CDD scheme is to be applied.

In some implementations, in determining whether to apply the CDD scheme,processor 412 may determine to apply the CDD scheme to enhance ULtransmission diversity in an event that the PUSCH transmission is a partof an URLLC.

In some implementations, in determining whether to apply the CDD scheme,processor 412 may determine to apply the CDD scheme in case of agrant-based or configured grant.

In some implementations, in determining whether to apply the CDD scheme,processor 412 may determine to apply the CDD scheme to achieve a targetreliability. In some implementations, in determining to apply the CDDscheme to achieve the target reliability, processor 412 may determine toapply the CDD scheme to achieve a BLER lower than or equal to a BLERthreshold. In some implementations, in determining whether to apply theCDD scheme, processor 412 may determine to apply the CDD scheme in anevent that a specific MCS table of a plurality of MCS tables is used forthe PUSCH transmission. In some implementations, the specific MCS tableof the plurality of MCS tables may include an MCS table for an URLLC.

In some implementations, in determining whether to apply the CDD scheme,processor 412 may determine to apply the CDD scheme in an event that aspecific RNTI of a plurality of RNTIs is used for the PUSCHtransmission.

In some implementations, in determining whether to apply the CDD scheme,processor 412 may determine to apply the CDD scheme in an event that anew modulation coding scheme radio network temporary identifier(MCS-RNTI) is used for the PUSCH transmission.

In some implementations, in determining whether to apply the CDD scheme,processor 412 may determine whether apparatus 410, implemented in a UE(e.g., UE 110), is configured with a capability of applying the CDDscheme for UL transmissions.

In some implementations, processor 412 may perform additionaloperations. For instance, processor 412 may receive, via transceiver416, a signaling from apparatus 420 indicating information related tomini-slot repetition. In such cases, in performing the PUSCHtransmission, processor 412 may perform the PUSCH transmission with atleast one symbol repeated in multiple mini-slots within a slot.

In some implementations, in receiving the signaling, processor 412 mayreceive an RRC signaling with the information related to mini-slotrepetition indicated by a new parameter defined in Rel-16 of the 3GPPspecification or an existing parameter defined in Rel-15 of the 3GPPspecification.

In some implementations, processor 412 may perform additionaloperations. For instance, processor 412 may perform a TBS calculationfor the PUSCH transmission with an assumption of no DMRS in the TBScalculation by maintaining a same TBS calculated from a DCI signalingfor all repetitions scheduled by the DCI signaling.

In another aspect of enhancement of NR PUSCH for URLLC in mobilecommunications in accordance with the present disclosure, processor 412of apparatus 410 may receive, via transceiver 416, a signaling fromapparatus 420 as a network node (e.g., network node 125) of a wirelessnetwork (e.g., wireless network 120) indicating information related tomini-slot repetition. Moreover, processor 412 may perform, viatransceiver 416, a PUSCH transmission to apparatus 420 with at least onesymbol repeated in multiple mini-slots within a slot.

In some implementations, in receiving the signaling, processor 412 mayreceive an RRC signaling with the information related to mini-slotrepetition indicated by a new parameter defined in Rel-16 of the 3GPPspecification or an existing parameter defined in Rel-15 of the 3GPPspecification.

In some implementations, processor 412 may perform additionaloperations. For instance, processor 412 may determine whether to apply aCDD scheme (e.g., non-transparent CDD) for the PUSCH transmission. Insuch cases, in performing the PUSCH transmission, processor 412 mayperform the PUSCH transmission with the CDD scheme applied responsive todetermining that the CDD scheme is to be applied.

In some implementations, in determining whether to apply the CDD scheme,processor 412 may perform one of the following: (i) determining to applythe CDD scheme to enhance UL transmission diversity in an event that thePUSCH transmission is a part of an URLLC; (ii) determining to apply theCDD scheme in case of a grant-based or configured grant; (iii)determining to apply the CDD scheme to achieve a target reliability;(iv) determining to apply the CDD scheme in an event that a specific MCStable of a plurality of MCS tables is used for the PUSCH transmission;(v) determining to apply the CDD scheme in an event that a specific RNTIof a plurality of RNTIs is used for the PUSCH transmission; (vi)determining to apply the CDD scheme in an event that a new MCS-RNTI isused for the PUSCH transmission; and (vii) determining whether apparatus410, implemented in a UE (e.g., UE 110), is configured with a capabilityof applying the CDD scheme for UL transmissions.

In some implementations, in determining to apply the CDD scheme toachieve the target reliability, processor 412 may determine to apply theCDD scheme to achieve a BLER lower than or equal to a BLER threshold. Insome implementations, the specific MCS table of the plurality of MCStables may include an MCS table for the URLLC.

In some implementations, processor 412 may perform additionaloperations. For instance, processor 412 may perform, by the processor, aTBS calculation for the PUSCH transmission with an assumption of no DMRSin the TBS calculation by maintaining a same TBS calculated from a DCIsignaling for all repetitions scheduled by the DCI signaling.

In yet another aspect of enhancement of NR PUSCH for URLLC in mobilecommunications in accordance with the present disclosure, processor 412of apparatus 410 may determine whether to apply a CDD scheme (e.g.,non-transparent CDD) for a PUSCH transmission. Additionally, processor412 may receive, via transceiver 416, a signaling from apparatus 420 asa network node (e.g., network node 125) of a wireless network (e.g.,wireless network 120) indicating information related to mini-slotrepetition. Moreover, processor 412 may perform a TBS calculation forthe PUSCH transmission with an assumption of no DMRS in the TBScalculation. Furthermore, processor 412 may perform, via transceiver416, the PUSCH transmission to apparatus 420 with the CDD scheme appliedin response to determining that the CDD scheme is to be applied.

In some implementations, in performing the PUSCH transmission, processor412 may perform the PUSCH transmission with at least one symbol repeatedin multiple mini-slots within a slot.

Illustrative Processes

FIG. 5 illustrates an example process 500 in accordance with animplementation of the present disclosure. Process 500 may be an exampleimplementation of the proposed schemes described above with respect toenhancement of NR PUSCH for URLLC in mobile communications in accordancewith the present disclosure. Process 500 may represent an aspect ofimplementation of features of apparatus 410 and apparatus 420. Process500 may include one or more operations, actions, or functions asillustrated by one or more of blocks 510 and 520. Although illustratedas discrete blocks, various blocks of process 500 may be divided intoadditional blocks, combined into fewer blocks, or eliminated, dependingon the desired implementation. Moreover, the blocks of process 500 mayexecuted in the order shown in FIG. 5 or, alternatively, in a differentorder. Process 500 may also be repeated partially or entirely. Process500 may be implemented by apparatus 410, apparatus 420 and/or anysuitable wireless communication device, UE, RSU, base station or machinetype devices. Solely for illustrative purposes and without limitation,process 500 is described below in the context of apparatus 410 as UE 110and apparatus 420 as network node 125. Process 500 may begin at block510.

At 510, process 500 may involve processor 412 of apparatus 410determining whether to apply a CDD scheme (e.g., non-transparent CDD)for a PUSCH transmission. Process 500 may proceed from 510 to 520.

At 520, process 500 may involve processor 412 performing, viatransceiver 416, the PUSCH transmission to apparatus 420 as a networknode (e.g., network node 125) of a wireless network (e.g., wirelessnetwork 120) with the CDD scheme applied responsive to determining thatthe CDD scheme is to be applied.

In some implementations, in determining whether to apply the CDD scheme,process 500 may involve processor 412 determining to apply the CDDscheme to enhance UL transmission diversity in an event that the PUSCHtransmission is a part of an URLLC.

In some implementations, in determining whether to apply the CDD scheme,process 500 may involve processor 412 determining to apply the CDDscheme in case of a grant-based or configured grant.

In some implementations, in determining whether to apply the CDD scheme,process 500 may involve processor 412 determining to apply the CDDscheme to achieve a target reliability. In some implementations, indetermining to apply the CDD scheme to achieve the target reliability,process 500 may involve processor 412 determining to apply the CDDscheme to achieve a BLER lower than or equal to a BLER threshold.

In some implementations, in determining whether to apply the CDD scheme,process 500 may involve processor 412 determining to apply the CDDscheme in an event that a specific MCS table of a plurality of MCStables is used for the PUSCH transmission. In some implementations, thespecific MCS table of the plurality of MCS tables may include an MCStable for an URLLC.

In some implementations, in determining whether to apply the CDD scheme,process 500 may involve processor 412 determining to apply the CDDscheme in an event that a specific RNTI of a plurality of RNTIs is usedfor the PUSCH transmission.

In some implementations, in determining whether to apply the CDD scheme,process 500 may involve processor 412 determining to apply the CDDscheme in an event that a new modulation coding scheme radio networktemporary identifier (MCS-RNTI) is used for the PUSCH transmission.

In some implementations, in determining whether to apply the CDD scheme,process 500 may involve processor 412 determining whether apparatus 410,implemented in a UE (e.g., UE 110), is configured with a capability ofapplying the CDD scheme for UL transmissions.

In some implementations, process 500 may involve processor 412performing additional operations. For instance, process 500 may involveprocessor 412 receiving, via transceiver 416, a signaling from apparatus420 indicating information related to mini-slot repetition. In suchcases, in performing the PUSCH transmission, process 500 may involveprocessor 412 performing the PUSCH transmission with at least one symbolrepeated in multiple mini-slots within a slot.

In some implementations, in receiving the signaling, process 500 mayinvolve processor 412 receiving an RRC signaling with the informationrelated to mini-slot repetition indicated by a new parameter defined inRel-16 of the 3GPP specification or an existing parameter defined inRel-15 of the 3GPP specification.

In some implementations, process 500 may involve processor 412performing additional operations. For instance, process 500 may involveprocessor 412 performing a TBS calculation for the PUSCH transmissionwith an assumption of no DMRS in the TBS calculation by maintaining asame TBS calculated from a DCI signaling for all repetitions scheduledby the DCI signaling.

FIG. 6 illustrates an example process 600 in accordance with animplementation of the present disclosure. Process 600 may be an exampleimplementation of the proposed schemes described above with respect toenhancement of NR PUSCH for URLLC in mobile communications in accordancewith the present disclosure. Process 600 may represent an aspect ofimplementation of features of apparatus 410 and apparatus 420. Process600 may include one or more operations, actions, or functions asillustrated by one or more of blocks 610 and 620. Although illustratedas discrete blocks, various blocks of process 600 may be divided intoadditional blocks, combined into fewer blocks, or eliminated, dependingon the desired implementation. Moreover, the blocks of process 600 mayexecuted in the order shown in FIG. 6 or, alternatively, in a differentorder. Process 600 may also be repeated partially or entirely. Process600 may be implemented by apparatus 410, apparatus 420 and/or anysuitable wireless communication device, UE, RSU, base station or machinetype devices. Solely for illustrative purposes and without limitation,process 600 is described below in the context of apparatus 410 as UE 110and apparatus 420 as network node 125. Process 600 may begin at block610.

At 610, process 600 may involve processor 412 of apparatus 410receiving, via transceiver 416, a signaling from apparatus 420 as anetwork node (e.g., network node 125) of a wireless network (e.g.,wireless network 120) indicating information related to mini-slotrepetition. Process 600 may proceed from 610 to 620.

At 620, process 600 may involve processor 412 performing, viatransceiver 416, a PUSCH transmission to apparatus 420 with at least onesymbol repeated in multiple mini-slots within a slot.

In some implementations, in receiving the signaling, process 600 mayinvolve processor 412 receiving an RRC signaling with the informationrelated to mini-slot repetition indicated by a new parameter defined inRel-16 of the 3GPP specification or an existing parameter defined inRel-15 of the 3GPP specification.

In some implementations, process 600 may involve processor 412performing additional operations. For instance, process 600 may involveprocessor 412 determining whether to apply a CDD scheme (e.g.,non-transparent CDD) for the PUSCH transmission. In such cases, inperforming the PUSCH transmission, process 600 may involve processor 412performing the PUSCH transmission with the CDD scheme applied responsiveto determining that the CDD scheme is to be applied.

In some implementations, in determining whether to apply the CDD scheme,process 600 may involve processor 412 performing one of the following:(i) determining to apply the CDD scheme to enhance UL transmissiondiversity in an event that the PUSCH transmission is a part of an URLLC;(ii) determining to apply the CDD scheme in case of a grant-based orconfigured grant; (iii) determining to apply the CDD scheme to achieve atarget reliability; (iv) determining to apply the CDD scheme in an eventthat a specific MCS table of a plurality of MCS tables is used for thePUSCH transmission; (v) determining to apply the CDD scheme in an eventthat a specific RNTI of a plurality of RNTIs is used for the PUSCHtransmission; (vi) determining to apply the CDD scheme in an event thata new MCS-RNTI is used for the PUSCH transmission; and (vii) determiningwhether apparatus 410, implemented in a UE (e.g., UE 110), is configuredwith a capability of applying the CDD scheme for UL transmissions.

In some implementations, in determining to apply the CDD scheme toachieve the target reliability, process 600 may involve processor 412determining to apply the CDD scheme to achieve a BLER lower than orequal to a BLER threshold. In some implementations, the specific MCStable of the plurality of MCS tables may include an MCS table for theURLLC.

In some implementations, process 600 may involve processor 412performing additional operations. For instance, process 600 may involveprocessor 412 performing, by the processor, a TBS calculation for thePUSCH transmission with an assumption of no DMRS in the TBS calculationby maintaining a same TBS calculated from a DCI signaling for allrepetitions scheduled by the DCI signaling.

FIG. 7 illustrates an example process 700 in accordance with animplementation of the present disclosure. Process 700 may be an exampleimplementation of the proposed schemes described above with respect toenhancement of NR PUSCH for URLLC in mobile communications in accordancewith the present disclosure. Process 700 may represent an aspect ofimplementation of features of apparatus 410 and apparatus 420. Process700 may include one or more operations, actions, or functions asillustrated by one or more of blocks 710, 720, 730 and 740. Althoughillustrated as discrete blocks, various blocks of process 700 may bedivided into additional blocks, combined into fewer blocks, oreliminated, depending on the desired implementation. Moreover, theblocks of process 700 may executed in the order shown in FIG. 7 or,alternatively, in a different order. Process 700 may also be repeatedpartially or entirely. Process 700 may be implemented by apparatus 410,apparatus 420 and/or any suitable wireless communication device, UE,RSU, base station or machine type devices. Solely for illustrativepurposes and without limitation, process 700 is described below in thecontext of apparatus 410 as UE 110 and apparatus 420 as network node125. Process 700 may begin at block 710.

At 710, process 700 may involve processor 412 of apparatus 410determining whether to apply a CDD scheme (e.g., non-transparent CDD)for a PUSCH transmission. Process 700 may proceed from 710 to 720.

At 720, process 700 may involve processor 412 receiving, via transceiver416, a signaling from apparatus 420 as a network node (e.g., networknode 125) of a wireless network (e.g., wireless network 120) indicatinginformation related to mini-slot repetition. Process 700 may proceedfrom 720 to 730.

At 730, process 700 may involve processor 412 performing a TBScalculation for the PUSCH transmission with an assumption of no DMRS inthe TBS calculation. Process 700 may proceed from 730 to 740.

At 740, process 700 may involve processor 412 performing, viatransceiver 416, the PUSCH transmission to apparatus 420 with the CDDscheme applied in response to determining that the CDD scheme is to beapplied.

In some implementations, in performing the PUSCH transmission, process700 may involve processor 412 performing the PUSCH transmission with atleast one symbol repeated in multiple mini-slots within a slot.

Additional Notes

The herein-described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely examples, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

Further, with respect to the use of substantially any plural and/orsingular terms herein, those having skill in the art can translate fromthe plural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

Moreover, it will be understood by those skilled in the art that, ingeneral, terms used herein, and especially in the appended claims, e.g.,bodies of the appended claims, are generally intended as “open” terms,e.g., the term “including” should be interpreted as “including but notlimited to,” the term “having” should be interpreted as “having atleast,” the term “includes” should be interpreted as “includes but isnot limited to,” etc. It will be further understood by those within theart that if a specific number of an introduced claim recitation isintended, such an intent will be explicitly recited in the claim, and inthe absence of such recitation no such intent is present. For example,as an aid to understanding, the following appended claims may containusage of the introductory phrases “at least one” and “one or more” tointroduce claim recitations. However, the use of such phrases should notbe construed to imply that the introduction of a claim recitation by theindefinite articles “a” or “an” limits any particular claim containingsuch introduced claim recitation to implementations containing only onesuch recitation, even when the same claim includes the introductoryphrases “one or more” or “at least one” and indefinite articles such as“a” or “an,” e.g., “a” and/or “an” should be interpreted to mean “atleast one” or “one or more;” the same holds true for the use of definitearticles used to introduce claim recitations. In addition, even if aspecific number of an introduced claim recitation is explicitly recited,those skilled in the art will recognize that such recitation should beinterpreted to mean at least the recited number, e.g., the barerecitation of “two recitations,” without other modifiers, means at leasttwo recitations, or two or more recitations. Furthermore, in thoseinstances where a convention analogous to “at least one of A, B, and C,etc.” is used, in general such a construction is intended in the senseone having skill in the art would understand the convention, e.g., “asystem having at least one of A, B, and C” would include but not belimited to systems that have A alone, B alone, C alone, A and Btogether, A and C together, B and C together, and/or A, B, and Ctogether, etc. In those instances where a convention analogous to “atleast one of A, B, or C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention, e.g., “a system having at least one of A, B, or C” wouldinclude but not be limited to systems that have A alone, B alone, Calone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc. It will be further understood by those withinthe art that virtually any disjunctive word and/or phrase presenting twoor more alternative terms, whether in the description, claims, ordrawings, should be understood to contemplate the possibilities ofincluding one of the terms, either of the terms, or both terms. Forexample, the phrase “A or B” will be understood to include thepossibilities of “A” or “B” or “A and B.”

From the foregoing, it will be appreciated that various implementationsof the present disclosure have been described herein for purposes ofillustration, and that various modifications may be made withoutdeparting from the scope and spirit of the present disclosure.Accordingly, the various implementations disclosed herein are notintended to be limiting, with the true scope and spirit being indicatedby the following claims.

What is claimed is:
 1. A method, comprising: determining, by a processor of an apparatus, whether to apply a cyclic delay diversity (CDD) scheme for a physical uplink shared channel (PUSCH) transmission; and performing, by the processor, the PUSCH transmission to a network node of a wireless network with the CDD scheme applied responsive to determining that the CDD scheme is to be applied.
 2. The method of claim 1, wherein the determining of whether to apply the CDD scheme comprises determining to apply the CDD scheme to enhance uplink (UL) transmission diversity in an event that the PUSCH transmission is a part of an ultra-reliable low-latency communication (URLLC).
 3. The method of claim 1, wherein the determining of whether to apply the CDD scheme comprises determining to apply the CDD scheme in case of a grant-based or configured grant.
 4. The method of claim 1, wherein the determining of whether to apply the CDD scheme comprises determining to apply the CDD scheme to achieve a target reliability.
 5. The method of claim 4, wherein the determining to apply the CDD scheme to achieve the target reliability comprises determining to apply the CDD scheme to achieve a block error rate (BLER) lower than or equal to a BLER threshold.
 6. The method of claim 1, wherein the determining of whether to apply the CDD scheme comprises determining to apply the CDD scheme in an event that a specific modulation coding scheme (MCS) table of a plurality of MCS tables is used for the PUSCH transmission.
 7. The method of claim 6, wherein the specific MCS table of the plurality of MCS tables comprises an MCS table for an ultra-reliable low-latency communication (URLLC).
 8. The method of claim 1, wherein the determining of whether to apply the CDD scheme comprises determining to apply the CDD scheme in an event that a specific radio network temporary identifier (RNTI) of a plurality of RNTIs is used for the PUSCH transmission.
 9. The method of claim 1, wherein the determining of whether to apply the CDD scheme comprises determining to apply the CDD scheme in an event that a new modulation coding scheme radio network temporary identifier (MCS-RNTI) is used for the PUSCH transmission.
 10. The method of claim 1, wherein the determining of whether to apply the CDD scheme comprises determining whether the apparatus, implemented in a user equipment (UE), is configured with a capability of applying the CDD scheme for uplink (UL) transmissions.
 11. The method of claim 1, further comprising: receiving, by the processor, a signaling from the network node indicating information related to mini-slot repetition, wherein the performing of the PUSCH transmission comprises performing the PUSCH transmission with at least one symbol repeated in multiple mini-slots within a slot.
 12. The method of claim 11, wherein the receiving of the signaling comprises receiving a radio resource control (RRC) signaling with the information related to mini-slot repetition indicated by a new parameter defined in Release 16 (Rel-16) of a 3^(rd) Generation Partnership Project (3GPP) specification or an existing parameter defined in Release 15 (Rel-15) of the 3GPP specification.
 13. The method of claim 1, further comprising: performing, by the processor, a transport block size (TBS) calculation for the PUSCH transmission with an assumption of no demodulation reference signal (DMRS) in the TBS calculation by maintaining a same TBS calculated from a DCI signaling for all repetitions scheduled by the DCI signaling.
 14. A method, comprising: receiving, by a processor of an apparatus, a signaling from a network node of a wireless network indicating information related to mini-slot repetition; and performing, by the processor, a physical uplink shared channel (PUSCH) transmission to the network node with at least one symbol repeated in multiple mini-slots within a slot.
 15. The method of claim 14, wherein the receiving of the signaling comprises receiving a radio resource control (RRC) signaling with the information related to mini-slot repetition indicated by a new parameter defined in Release 16 (Rel-16) of a 3^(rd) Generation Partnership Project (3GPP) specification or an existing parameter defined in Release 15 (Rel-15) of the 3GPP specification.
 16. The method of claim 14, further comprising: determining, by the processor, whether to apply a cyclic delay diversity (CDD) scheme for the PUSCH transmission, wherein the performing of the PUSCH transmission comprises performing the PUSCH transmission with the CDD scheme applied responsive to determining that the CDD scheme is to be applied.
 17. The method of claim 16, wherein the determining of whether to apply the CDD scheme comprises performing one of: determining to apply the CDD scheme to enhance uplink (UL) transmission diversity in an event that the PUSCH transmission is a part of an ultra-reliable low-latency communication (URLLC); determining to apply the CDD scheme in case of a grant-based or configured grant; determining to apply the CDD scheme to achieve a target reliability; determining to apply the CDD scheme in an event that a specific modulation coding scheme (MCS) table of a plurality of MCS tables is used for the PUSCH transmission; determining to apply the CDD scheme in an event that a specific radio network temporary identifier (RNTI) of a plurality of RNTIs is used for the PUSCH transmission; determining to apply the CDD scheme in an event that a new modulation coding scheme radio network temporary identifier (MCS-RNTI) is used for the PUSCH transmission; and determining whether the apparatus, implemented in a user equipment (UE), is configured with a capability of applying the CDD scheme for UL transmissions.
 18. The method of claim 17, wherein the determining to apply the CDD scheme to achieve the target reliability comprises determining to apply the CDD scheme to achieve a block error rate (BLER) lower than or equal to a BLER threshold, and wherein the specific MCS table of the plurality of MCS tables comprises an MCS table for the URLLC.
 19. The method of claim 14, further comprising: performing, by the processor, a transport block size (TBS) calculation for the PUSCH transmission with an assumption of no demodulation reference signal (DMRS) in the TBS calculation by maintaining a same TBS calculated from a DCI signaling for all repetitions scheduled by the DCI signaling.
 20. A method, comprising: determining, by a processor of an apparatus, whether to apply a cyclic delay diversity (CDD) scheme for a physical uplink shared channel (PUSCH) transmission; receiving, by the processor, a signaling from a network node of a wireless network indicating information related to mini-slot repetition; performing, by the processor, a transport block size (TBS) calculation for the PUSCH transmission with an assumption of no demodulation reference signal (DMRS) in the TBS calculation; and performing, by the processor, the PUSCH transmission to the network node with the CDD scheme applied responsive to determining that the CDD scheme is to be applied, wherein the performing of the PUSCH transmission comprises performing the PUSCH transmission with at least one symbol repeated in multiple mini-slots within a slot. 